Release 10.1A: OpenEdge Data Management:
Database Administration

Using the Windows Cluster Administrator

The Windows Cluster Administrator is a powerful and intuitive graphical user interface that allows a user with administrator privileges the ability to tailor the cluster environment. Once you open a connection to your cluster, the administrator browser displays Groups, Resources, Cluster Configuration, and the member nodes as the primary selection objects. Each of the objects can be expanded to display their contents much like Windows Explorer. Resources can be moved from group to group simply by dragging and dropping them. For more information on using the Cluster Administrator, see your Microsoft documentation. The next steps detail how to create and manage database resources with the Cluster Administrator.

To create a database resource with Cluster Administrator:

Open a connection to your cluster and select New Resource for the group where you are adding the database.
Fill in the dialog box as follows:
Fill in Name with the name of the resource. The fully qualified name of the database is the recommended value.
Fill in Description with anything meaningful to the user.
Select OpenEdge Database for Resource type.
Group should default to the one you selected in Step 1.
Check Run this resource in a separate resource monitor.
Select the preferred node default of any node.
Select the disk(s) and cluster name (or IP address) as resources the database depends on.
Fill in the Parameters table for the database resource as follows:
Enter the fully qualified name of the database for Database File Spec.
Enter the fully qualified path to the working directory of your OpenEdge install for Working Directory.
Enter the name of the command to start the database for Start Command. For example, C:\Progress\OpenEdge\bin\_mprosrv. Enter only the name of the command, not the complete command line to execute.
Supply the options normally specified on the command line in Start Options. For example, -pf <parameter-file>.
Enter the command used to shutdown the database in Stop Command. For example, C:\Progress\OpenEdge\bin\proshut. Enter only the name of command. Do NOT include the database file specification.
Enter the options normally used to shutdown the database in Stop Options. For example, -by.
Select Finish to complete the operation. The database resource will be displayed in the Explorer window in the Offline state.

Once the database resource is created, it can be started and shut down through the Cluster administrator.

To start the database, right click on the database resource and select Bring Online. The state of the database resource will change from Offline, to Online Pending, to Online in the Explorer window as the database completely starts up.

To shut down the database, right click the resource name and select Take Offline. The state of the database will change from Online, to Offline Pending, to Offline once the database has completely shut down.

To Add a secondary broker to a cluster-enabled database with Cluster Administrator:

Select Resources from the tree view.
Select your database resource.
Select File New Resource. The New Resource dialog box appears.
Proceed through the configuration of the new resource.
For Name, enter the name you want for the secondary broker resource.
For Resource type, chose Progress Database.
For Possible owners, chose the same hosts as you selected for your database.
For Dependencies, chose your database.
When you have completed the configuration, bring up the Properties dialog box, and fill in the Parameters table for the database resource as follows:
Enter the fully qualified name of the database for Database File Spec.
Enter the fully qualified path to the working directory of your OpenEdge install for Working Directory.
Enter the name of the command to start the database for Start Command. For example, C:\Progress\OpenEdge\bin\_mprosrv. Enter only the name of the command, not the complete command line to execute.
Supply the options normally specified on the command line to start a secondary broker in Start Options. For example, -pf start_secondary_brkr.pf.
Leave Stop Command and Stop Options blank. Shutdown of the database is handled by the commands specified with the primary broker.

If you want to start more than one secondary broker, modify the procedure to specify a .bat file for the Start Command entered in Step 5. The .bat file must contain the command lines to start the secondary brokers.